I'm in two minds about this; it seems like the most likely outcome here is simply: slower builds - I can't really recall any scenarios where we've had macos specific problems, and in reality macos is very much the minority anticipated execution environment. I'm all for it working, but I'm not sure we need to run it for every PR/commit.

What's your thoughts, @NickCraver, as someone with more of a CI overview?

As a secondary observation:

Run docker compose -f docker-compose.yml up -d --wait
/Users/runner/work/_temp/739e6771-49b7-4f5d-b7df-37bbbd88d8b2.sh: line 1: docker: command not found
Error: Process completed with exit code 127.

As a secondary observation:

Run docker compose -f docker-compose.yml up -d --wait
/Users/runner/work/_temp/739e6771-49b7-4f5d-b7df-37bbbd88d8b2.sh: line 1: docker: command not found
Error: Process completed with exit code 127.

I thought it would be simple, but looks like docker is not supported yet https://stackoverflow.com/questions/77675906/github-actions-build-docker-image-on-arm64-macos-latest-xlarge

it seems like the most likely outcome here is simply: slower builds
I'm not sure about this one, as the pipelines will run concurrently, and the Windows build is relatively slow

I thought it would be simple, but looks like docker is not supported yet

So should we shelve this for the foreseeable?

We shouldn't add this - it doesn't add value but does eat build minutes we have limited capacity of :)